UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The IDPS must enforce information flow control using explicit security attributes on information, source, and destination objects as a basis for flow control decisions.


Overview

Finding ID Version Rule ID IA Controls Severity
V-34488 SRG-NET-000020-IDPS-00022 SV-45268r1_rule Medium
Description
Information flow control regulates where information is allowed to travel within a network and between interconnected networks. The flow of all network traffic must be monitored and controlled, so it does not introduce any unacceptable risk to the network infrastructure or data. Restrictions can be enforced based on source and destination IP addresses, as well as the ports and services being requested. This requirement should enforce the deny-by-default policy whereby only the known and accepted traffic will be allowed outbound and inbound. For IDPS implementation, this control applies to communications with other IDPS components and other network elements. These communications may include sensor log aggregation, software updates, and firewall ACL updates. Non-explicit attributes may include MAC addresses or other easily changed device information.
STIG Date
Intrusion Detection and Prevention Systems (IDPS) Security Requirements Guide 2012-11-19

Details

Check Text ( C-42615r1_chk )
Examine the configuration on the IDPS.
Verify source and destination IP addresses are used as a basis for information flow between IDPS components or communications with other network elements.

If non-explicit attributes are used for information flow control, this is a finding. If source and destination IP addresses are not used, this is a finding.
Fix Text (F-38664r1_fix)
Configure the network configuration on the sensors for external communications using source and destination IP addresses.